Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue #55 #56

Merged
merged 4 commits into from
Sep 2, 2018
Merged

Issue #55 #56

merged 4 commits into from
Sep 2, 2018

Conversation

Developer-Matt
Copy link

Ignore hidden excel sheets when importing
Additional, trim cell values before processing

Ignore hidden excel sheets when importing
Additional, trim cell values before processing
@coveralls
Copy link

coveralls commented Aug 13, 2018

Coverage Status

Coverage decreased (-0.5%) to 87.234% when pulling f56f9eb on Developer-Matt:master into 9b0a563 on ozlerhakan:master.

@ozlerhakan
Copy link
Owner

Hi @Developer-Matt ,

Thank you for your PR!, could you please provide one test for that case as well?

@Developer-Matt
Copy link
Author

Hi,
Yes will write up some test cases for my changes as soon as I can.

@Developer-Matt
Copy link
Author

All done. Please let me know if you would like any more additional specific test.

Matt

@ozlerhakan
Copy link
Owner

Thanks @Developer-Matt , I will look at the changes

@ozlerhakan
Copy link
Owner

Hi @Developer-Matt ,

I found that you get the first visible sheet from the excel file. However, what if we have more than one visible sheets in an excel and we need to retrieve the second visible sheet among them?

@Developer-Matt
Copy link
Author

Hi,

Ah yes I see your point, I have re written the method that finds which sheet to use, to now consider if a specified sheet index was requested. Have also created additional test cases for this.

@ozlerhakan
Copy link
Owner

Thanks @Developer-Matt , I will merge your PR soon with small changes

@ozlerhakan
Copy link
Owner

Hi @Developer-Matt ,

After testing the changes, I found that we should consider another way of implementing xlsx part because I get "gc overhead limit exceeded exception" when loading 187k rows of an excel file. We have two options, we can learn how to do the same functionality differently or we can only support this feature for xls files.

@@ -39,6 +42,12 @@

<T> void unmarshal0(Class<T> type, Consumer<? super T> consumer, OPCPackage open) throws IOException, SAXException, OpenXML4JException {

//ISSUE #55
XSSFWorkbook wb = new XSSFWorkbook(open);
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is the statement where I get "gc exception". @Developer-Matt

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It kinda makes sense as to why it does that, but that's annoying. At the moment I am using my version and we are not importing that number of rows, so I would like to try and find a way to fix this before forced to limit only to xls. So unless there are other developers that need this functionally now, can you hold of on doing the pull and I will do some investigating and let you know what I find.

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

no problem, I will inform you as well if I find something useful for this case.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey, I have done some work on a different way to find hidden and visible sheets to avoid the GC exception. Can you please have a look at it when you get a chance and see if its an ok way to do it, and if it makes sense and if passes your 187k test. Have also included some big excel files for tests, hope they are not to large for repo.

The code still needs to be tidied up and made neater but just would like you to have a look first. If you happy with it I will go and tidy it all up and then can merge.

Thanks

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @Developer-Matt , good news is that all tests pass successfully yay! :) , I will look at the changes you have made and will make some changes If necessary.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awesome. Cool, I will go clean up and comment my code quick

…it exceeded exception.

Just proof of concept, still needs to be tidied up
@ozlerhakan ozlerhakan merged commit f56f9eb into ozlerhakan:master Sep 2, 2018
@ozlerhakan
Copy link
Owner

Thank you very much @Developer-Matt , now merged!  🎉

@Developer-Matt
Copy link
Author

Awesome thanks, I did just do another push, I tidied up and commented my code. Not sure if you would like the cleaner code, can create a new pull request but seems a waste, let me know.
I will also be doing some more updates soon so can also get the cleaner code then

@ozlerhakan
Copy link
Owner

Hi @Developer-Matt ,
I have tried the code cleaner but it may need more work. so do not hesitate to do that If you want.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants